- MyVidCap is now compiled using 603 / "G3" processor instruction scheduling, which may add a small boost to performance especially on G3 PowerMacs.
- I added the ability to Graph the frame rate of a movie (Movie Menu > Graph Frame Rate…). You can use this to look at the frequency of each video frames duration for either the entire movie (nothing selected) or only the a selected portion of a movie (just hilite the selection you want to graph). This is primarily a diagnosis tool to indicate how regular your video capturing is.
- I added another diagnostic tool for determining what a particular AV card and it's Drivers can do (Digitzer Menu > Digitizer Info… item). I'm not going to go into details, but it determines the various capabilities of the video card your using (dimensions it can capture at, color depths, special features etc.). If your having problems capturing video, please select this item and then do a screen snap shot of the dialog (Command Shift 3 or Command Shift 4)with all it's settings. It might help me diagnose a particular problem your having.
- I finally resolved the problem with capturing audio to the Ram inside MyVidCap (and video to disk) with QuickTime 3.0 and the capture duration being limited to about 55 to 75 seconds before either Quicktime reported it had run out of Ram or it would start choking and dropping frames (0.5 fps when this happened). The Soundmanager and Quicktime are fighting over memory allocation for recorded audio and we had to do some really snarky programming to work around it (not low level type hacks - just making sure the two of them weren't working at cross purposes for memory allocation - enough said about this). So you can now reliably record audio to Ram inside MyvidCap. We actually recommend you DO capture audio to the ram inside MyVidcap, as you'll get more consistent recording than using Temporary memory, as well as there is far less delay between when you type "Command - R" to begin recording and the actual recording starts.
- MyVidCap can now record up to 24 gigabytes of AV per recording session, assuming you have that much space available.
To enable extended/daisy chain recording, Open the video Window, Click on the Digitizer menu and select the Preferences… item.
In the Recording Prefs dialog, select the hard drives - partions you want to record too using the Select 1st Capture Location and Select 2nd Capture Location buttons. Make sure you Check mark the "Daisy Chain to" checkbox too.
1) If you have one huge hard drive (greater than 2 gigs), make sure that the first and second capture locations are selected on this drive. Then my vidcap will record up to 24 gigs of AV data to it (12 two gigabyte movie files on this drive).
2) If you have 2 hard drives or 2 hard drive partions selected, MyVidCap will record up to 2 gigabytes of video on the 1st capture location you select, and will fill up the the 2nd Capture location to a maximum limit of 22 gigs (11 two gigabyte movie files on this drive).
Once you begin recording, MyVidCap will continue to record to multiple 2 gigabyte (maximum 12 two gig size) movie capture files until all disk space is consumed or you click the mouse button to stop recording.
When you want to SAVE the huge multi-gigabyte files without re-compressing / flattening them. Do the following:
1) Make sure no part of the movie you captured is selected / hilighted.
2) Select Save… (or Command S).
3) MyVidCap will prompt you for a 31 character name to re-name the capture file(s) to.
4) Fill in the name you want and click Okay. MyVidcap will simply change the file names and your movie(s) are saved.
Any capture files (both video and audio if you split them up) that were recorded for this movie will be renamed using the name you entered. So if you captured 5 gigabytes of video (which would be split up into three video movies) and 1 audio movie, Saved and re-named this to to "My Clips", you would get the following:
A controlling movie called "My Clips", 2 other movies named "My Clips V1" and "My Clips V2" which have the video in them and "My Clips A" which has the Audio in it. Do not delete the controlling or other movie files or you may wind up not being able to play them again (except the Audio one).
NOTE to Barracuda HardDrive Owners. Recording video, Recording Audio or Recording Audio and Video to RAM (either temporary memory or memory inside) MAY CAUSE complete Mac lockups - regardless of the QuickTime version installed (2.5 or 3) or the QuickTime recording Application (we've duplicated this on 4 of them to date) your using - IF your recording to a Barracuda HardDrive AND the drive has been low level formatted using APS Power Tools 4.1 and your using MacOS 8.0 or 8.1. This problem does not occur if your using a barracuda drive that has been low level formatted with FWB 2.06 & FWB 2.5.2 or Apple's HardDrive formatting software. The drive formatted with APS 4.1 may function fine for normal day to day use or recording to disk, but will not work if you record to Ram and then record to disk later. We don't know why this happens, but it does.
Version 2.07 fixes the following things.
- Freeze on any mac not using OS 8.1 as soon as you try to pull up the Video Window.
This was introduced when we attempted to fix the G3 audio problem (2.03 and up). The problem stems from some misinformation on the soundmanager in OS 8.1 and whether this applies to earlier version of the sound manager or is strictly an "OS 8.1" feature. My "interpretation" the technotes seemed to indicate it was sound manager version dependent, however it is actually "OS 8.1" only. Anyhow it's fixed..
- The G3 owners should be able to hear and record audio without the audio being re-set after closing video windows. The Audio settings should now "Stick" after you check the "Force Audio Inputs" item at the Bottom of the Digitizer Menu.
- People using QuickTime 2.5 will not be able to "Record To Ram" if they have Audio recording "split" to another hard drive. In the Recording Preferences dialog uncheck the "Save Audio to" item and then Ram capture will be enabled. We disabled it because it would not work reliably or could cause Type 3 crash errors with QuickTime 2.5. It works fine under QuickTime 3.0 and OS 8.0 or 8.1.
